-
Notifications
You must be signed in to change notification settings - Fork 1.1k
[CI] Prepare for 3.8.0-RC1 release #24422
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
|
||
| publish-winget: | ||
| uses: ./.github/workflows/publish-winget.yml | ||
| if: false # TODO: Requires setting up initial WinGet package |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Didn't this work previously?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, never, see #22184
…expose implementation detail in POM metadata
| .dependsOn(`scala3-interfaces`, `tasty-core-bootstrapped-new`, `scala3-library-bootstrapped-new`) | ||
| .settings(publishSettings) | ||
| .settings( | ||
| name := "scala3-compiler-bootstrapped", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
these are not necessary to remove, the moduleName two lines below is what defines the name of the artifact. We should keep these to know in sbt if we manipulate a bootstrapped project or a on-bootstrapped project.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but these are later exposed publicly as attributes in POM https://repo1.maven.org/maven2/org/scala-lang/scala3-compiler_3/3.7.4/scala3-compiler_3-3.7.4.pom - see both name and description
The non-bootstrapped projects have the nonbootstrapped suffix, so it should be fine
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll accept this PR assuming that the non-bootstrapped projects are label.
| fi | ||
| - name: Prepare the SDKs | ||
| shell: bash |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't have the binaries yet.
| - name: Download MSI package | ||
| uses: actions/download-artifact@v6 | ||
| with: | ||
| name: scala.msi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and we don't have the msi yet
…need to expose implementation detail in POM metadata" This reverts commit b340f1c.
Prepare for releasing 3.8.0-RC1 artifacts by adjusting how artifacts are published. We don't introduce a full refactor by switching to use dedicated environments and `release-maven-artifacts` workflow yet. Instead we're only adjusting existing, battle-tested workflow to publish artifacts using new variants of projects to reduce risks due too many moving parts. The CI refactor would be introduced for 3.8.1 releases after testing it first on nightlies in a full workflow (including execution of tests which is now missing) Additional minor adjustments: - disable publishing to WinGet - this workflow has never succeeded and requires creation of first release manually - Switch homepage from GitHub repository to `scala-lang.org` website [Cherry-picked 7a0d2be]
Backports #24422 to the 3.8.0-RC1. PR submitted by the release tooling.
Prepare for releasing 3.8.0-RC1 artifacts by adjusting how artifacts are published.
We don't introduce a full refactor by switching to use dedicated environments and
release-maven-artifactsworkflow yet. Instead we're only adjusting existing, battle-tested workflow to publish artifacts using new variants of projects to reduce risks due too many moving parts.The CI refactor would be introduced for 3.8.1 releases after testing it first on nightlies in a full workflow (including execution of tests which is now missing)
Additional minor adjustments:
scala-lang.orgwebsite